re > sectioning > chapter @ level 2 : 0.1 -> MetaPost
pages > flushing realpage 1, userpage 1, subpage 1
metapost> initializing instance 'metafun:1' using format 'metafun' and
method 'double'
metapost> loading 'metafun' as
'C:/Users/adeim/
eyword
extraction from MetaFun's source code. By fine-grained, I mean that the
output contains information about the kind of keyword (def, primary def,
vardef, constant, variable, etc.) I could update it to Lua and mp-*.mpxl
if that interests you—unless that has already been done, of course.
t in the past for fine-grained keyword
extraction from MetaFun's source code. By fine-grained, I mean that the
output contains information about the kind of keyword (def, primary def,
vardef, constant, variable, etc.) I could update it to Lua and mp-*.mpxl
.. in mpxl we use names like
temp_pair_z
i.e. a temp_ namespace (as well as a mfun_ one) for all these
potentially clashing short names
you could do
newinternal n_; pair z_[],dz_;
at the top of your file (because we don't use them) but stil ...
Hans
' yearly current release
but of course after that there will be updates when needed. In these
updates we don't distinguish between betas and currents: we dropped that
some time ago because it was only confusing.
Last/this year much of LMTX (mkxl, mpxl, lmt files) already got split
and I expect
> log >
resolvers > methods > resolving, method 'finders', how 'uri',
handler 'file', argument 'boxrow.mp'
in 2021.01.24:
resolvers > tex > 'file' closer:
'/local/Software/lmtx/tex/texmf-context/metapost/context/base/mpxl/metafun.mpxl
is as an experiment: primitives, permanent, immutable
> and mutable (so far); you can look at the *.mpxl files to get an idea. If you
> say for instance
>
>path fullcircle;
>
> there will be a warning
>
> metapost> overloading immutable 'fullcircle'
, immutable and mutable (so far); you can look at the *.mpxl files to get an idea. If you say for instance path fullcircle; there will be a warning metapost > overloading immutable 'fullcircle' or when \enabledirectives[metapost.overloadmode=error] has b
can do something similar in metapost: flag macros
and variables in order to issue a warnings when a dangerous overload
happens.
The current lmtx has this as an experiment: primitives, permanent,
immutable and mutable (so far); you can look at the *.mpxl files to get
an idea. If you say
problems; but context --make has
> this error.
>
> Do I miss something?
>
> Thanks
> Christian
>
> Am Mo., 23. Nov. 2020 um 18:56 Uhr schrieb Hans Hagen :
> Hi,
>
> I uploaded a next iteration of lmtx. From now on there are dedicated sub
> directories for mkl
Mo., 23. Nov. 2020 um 18:56 Uhr schrieb Hans Hagen :
> Hi,
>
> I uploaded a next iteration of lmtx. From now on there are dedicated sub
> directories for mklx and mpxl, which is an indication that we're on the
> way to a full co
On 11/23/20 6:55 PM, Hans Hagen wrote:
> Hi,
>
> I uploaded a next iteration of lmtx. From now on there are dedicated sub
> directories for mklx and mpxl, which is an indication that we're on the
> way to a full code split.
Hi Hans,
I’m afraid that there is an error that preven
Hi,
I uploaded a next iteration of lmtx. From now on there are dedicated sub
directories for mklx and mpxl, which is an indication that we're on the
way to a full code split.
Hans
13 matches
Mail list logo
